-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove x-ms-long-running-operation-options from MFE spec #17823
Remove x-ms-long-running-operation-options from MFE spec #17823
Conversation
Hi, @erjms Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Rule | Message |
---|---|
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L5965 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L6002 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L6926 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L7286 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L7667 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L7691 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L7699 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L8290 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L8392 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L9256 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L9349 |
R2008 - MutabilityWithReadOnly |
When property is modeled as 'readOnly': true then x-ms-mutability extension can only have 'read' value. When property is modeled as 'readOnly': false then applying x-ms-mutability extension with only 'read' value is not allowed. Extension contains invalid values: 'read'. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L9373 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L71 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L121 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L171 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L234 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L305 |
R4039 - ParametersOrder |
The parameters:endpointName,deploymentName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L376 |
R4039 - ParametersOrder |
The parameters:endpointName,deploymentName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L433 |
R4039 - ParametersOrder |
The parameters:endpointName,deploymentName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L490 |
R4039 - ParametersOrder |
The parameters:endpointName,deploymentName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L561 |
R4039 - ParametersOrder |
The parameters:endpointName,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L640 |
R4039 - ParametersOrder |
The parameters:name,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L743 |
R4039 - ParametersOrder |
The parameters:name,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L793 |
R4039 - ParametersOrder |
The parameters:name,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L843 |
R4039 - ParametersOrder |
The parameters:name,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L914 |
R4039 - ParametersOrder |
The parameters:name,version,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L985 |
R4039 - ParametersOrder |
The parameters:name,version,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L1042 |
R4039 - ParametersOrder |
The parameters:name,version,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L1099 |
R4039 - ParametersOrder |
The parameters:name,resourceGroupName,workspaceName should be kept in the same order as they present in the path. Location: Microsoft.MachineLearningServices/preview/2021-03-01-preview/mfe.json#L1228 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
Hi @erjms, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Removed from 2021-03-01-preview api version for non-POST LRO operations. Non-breaking change to fix autogenerated REST clients.
6745f10
to
d90824a
Compare
* Removed x-ms-long-running-operation-options from MFE spec Removed from 2021-03-01-preview api version for non-POST LRO operations. Non-breaking change to fix autogenerated REST clients. * Fixed validation errors in examples for MFE 2021-03-01-preview api version
Removed from 2021-03-01-preview api version. Non-breaking change to fix autogenerated REST clients.
Context: AML services follow ARM guidelines when returning payloads after long-running operation polling terminates. They do not return payloads consistent with the x-ms-long-running-operation-options spec. This was not caught as an issue prior to this point because this property was not utilized by REST clients. However, that has changed, and so removing this property from the spec should resolve any issues those clients have with AML long-running operations.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
N/A
February 2022
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.